Overview

The Euclid API is designed to facilitate interactions with the Euclid platform, enabling users to perform a variety of actions such as querying data, executing transactions, and more. This documentation aims to provide comprehensive information on how to use the API, including details on available endpoints, request and response formats, and example usages.

The Euclid API is built using GraphQL, a powerful query language for APIs that allows clients to request exactly the data they need. This approach avoids both the problems of over and under-fetching data, while also allowing for a more powerful and flexible API.

note

• Before reading these docs and using the API, it is recommended you familiarise yourself with GraphQL by reading the official GraphQL documentation.

In addition to the GraphQL API, Euclid also provides a REST API, a traditional and widely-used approach for accessing web services. The REST API is mostly used to generate transactions that can be signed by a wallet and broadcast to chains.

Available Queries

In the following sections, we will be covering all the available queries for the following:

note

Factory queries are only applicable to Cosmos-based chains. For EVM chains, use the corresponding router query as an alternative.

• Chains: Query chain information.
• Factory: Query information from the factory contract.
• Router: Query information from the router contract.
• VLP: Query information from VLP contracts.
• VCoin: Query information from the Virtual Balance contract.
• Pool: Get information on Euclid pools such as liquidity and volume.
• Token: Get token metadata for tokens.
• CW: Get information on a LP Tokens.

GraphQL Endpoints

note

Examples in this API reference now use mainnet endpoints by default. If you need testnet, replace api.euclidprotocol.com with testnet.api.euclidprotocol.com.

Mainnet: https://api.euclidprotocol.com/

Testnet: https://testnet.api.euclidprotocol.com

REST API

In addition to the GraphQL API, the Euclid platform also provides a REST API for various operations. Below are the available REST API sections we will cover:

• Routes: Get the available routes for a swap.
• Transaction: Generate transactions for various calls such as making swaps and adding/removing liquidity.

Common HTTP Responses

The backend Swagger currently documents these common REST response codes:

Code	Meaning	Typical Cause
200	Success	The request was accepted and returned data or generated transaction payloads successfully.
400	Bad Request	Missing fields, invalid query params, malformed JSON, or request validation failures.
401	Unauthorized	Authentication headers or tokens are required but missing or invalid.
403	Forbidden	A secret token or protected action was provided but is not allowed for the caller.
404	Not Found	The requested resource, object, or record could not be found.
500	Internal Server Error	The backend failed while processing the request or fetching dependent data.

note

The current backend Swagger in the API repo documents 200, 400, 401, 403, 404, and 500. It does not currently document 504.